Final lifecycle quality / consistency updates #388
Open
mindthegab wants to merge 23 commits intomainfrom
Open
Conversation
✅ Deploy Preview for eager-borg-83c1a5 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
…o incubation, cleaned up lifecycle homepage, moved ooutside of software projects as it applies also to standards
…oved out of software projects only
mindthegab
force-pushed
the
final-lifecycle-updates
branch
from
5506412 to
efd805a
Compare
eddie-knight
approved these changes
Feb 23, 2026
mindthegab
requested review from
TheJuanAndOnly99 and
maoo
and removed request for
TheJuanAndOnly99
Co-authored-by: Juan Estrella <juan.estrella@finos.org>
psmulovics
reviewed
Feb 23, 2026
|
|
||
| To graduate into the Graduated stage, a project must meet the requirements of the [Graduated Lifecycle Checklist](/docs/governance/lifecycle-stages/graduated#Graduated+Acceptance+Requirements) and [Graduated ongoing maintenance requirements](/docs/governance/lifecycle-stages/graduated#Graduated+Ongoing+Maintenance+Requirements). | ||
|
|
||
| Any project maintainer may request Graduation by opening a [project graduation request](https://github.com/finos/community/issues/new?assignees=maoo%2C+TheJuanAndOnly99&labels=&template=Project-Graduation.md&title=projectName+Graduation+request) with an information packet demonstrating that they've met the requirements for activation (see below for details). |
Contributor
There was a problem hiding this comment.
Should we have the assignees as a github team?
Open
17 tasks
3 tasks
eddie-knight
reviewed
Mar 8, 2026
|
|
||
| Optionally, before a project is formally contributed (in either [Labs](/docs/governance/lifecycle-stages/labs) or Incubating stage), a FINOS Platinum Member might request to work privately with other prospective contributor FINOS Members to gauge viability and evaluate interest ahead of formal contribution during what's referred as "formation". | ||
|
|
||
| Projects which successfully complete the Formation stage are expected to become fully open source within one year. |
Contributor
There was a problem hiding this comment.
I've been thinking about how the DTCC hackathons are currently done, and whether all hackathon repos should belong in Labs. It's established that FINOS needs to host those repos... Would the Formation status be appropriate for those projects?
Maybe the only difference would be the logistics behind the scenes, based on whether it's a platinum donation or hackathon.
Member
There was a problem hiding this comment.
Hi @eddie-knight we're discussing this internally and we're looking into creating a new hackathon specific GitHub Org to house hackathon related repositories.
* refactor issue templates * Update placeholder for GitHub profiles field * Update placeholder format in community recognition template * Refactor project archival issue template structure Reorganize markdown and textarea fields in the archival issue template. * Refactor archival issue template formatting Removed unnecessary markdown type and adjusted value formatting for archival reason. * Refactor project archival issue template Updated the archival issue template to streamline the input fields and improve clarity. * Revise community participation criteria in issue template Updated the community participation criteria to require 3 independent individuals and/or organizations, including a FINOS member, and added usage requirements. * Create Project Graduation issue template Add a new issue template for Project Graduation with detailed criteria and checklist for FINOS hosted projects. * Rename project_archiviation.yml to project_archival.yml * Update graduation link in issue template * Update link for project archival reasons * Delete .github/ISSUE_TEMPLATE/Project-Graduation.md * New issue (#6) * Create unified Contribution and Onboarding issue template * Enhance descriptions in contribution issue template Updated descriptions and placeholders for clarity in the issue template. * Add project incubation issue template This YAML file defines a template for project incubation requests, including sections for entry path, acceptance requirements, maintenance commitments, and final steps. * Add links to OpenSSF Security Baseline in template * Revise project graduation issue template Updated the project graduation issue template to reflect changes in naming, descriptions, and structure for clarity and compliance with FINOS standards. * Update labels for project graduation template * Update project archival issue template * Update software_project_contribution.yml * Update software_project_contribution.yml * Update contribution template with advanced stage info Added next steps for advanced stages in contribution template. * Update contribution checklist confirmation label Expanded the confirmation label for operational completion to include approval details for Labs stage and TOC. * Enhance software project contribution template Updated descriptions and labels for clarity in the software project contribution template. * Revise maintainer team details and descriptions Updated maintainer team section and improved descriptions. * Update section headers in project incubation template * Update markdown headers for archival issue template * Update section titles in project graduation template * Update project_archival.yml * Update archival acknowledgment requirements in template * Update archival template to include markdown implications Replaced checkbox requirements with markdown implications for project archival. * Update software_project_contribution.yml * Update software_project_contribution.yml * Revise archival acknowledgment and confirmation options Updated the archival acknowledgment section to clarify implications and required confirmations for project archiving. * Refactor maintainer acknowledgment checkboxes * Update software_project_contribution.yml * Fix validation requirement for socialization acknowledgment * Update software_project_contribution.yml * Update project incubation issue template validations * Update project_graduation.yml * Update project_graduation.yml * Update project_incubation.yml * Remove FINOS Community Governance requirement Removed "Project implements FINOS Community Governance structure" as it's unclear. @TheJuanAndOnly99 - what did you mean exactly? we would need to add a link to refer to any guidelines we ask people to adhere to. * Change assignee for community recognition issue * Add link to acceptance criteria docs Updated links to lifecycle stages and added acceptance requirements. * Add markdown separator to contribution template * Change required attribute for organization name field * Change project template from Incubation to Labs Updated project template from 'Incubation' to 'Labs' stage, modifying descriptions and requirements accordingly. * Update software project contribution link in Contribution.md Updated contribution proposal templates for software projects. * Update project_labs.yml * Update .github/ISSUE_TEMPLATE/project_graduation.yml Co-authored-by: Eddie Knight <knight@linux.com> * Update .github/ISSUE_TEMPLATE/project_incubation.yml Co-authored-by: Eddie Knight <knight@linux.com> * Update .github/ISSUE_TEMPLATE/software_project_contribution.yml Co-authored-by: Eddie Knight <knight@linux.com> * Update .github/ISSUE_TEMPLATE/project_incubation.yml Co-authored-by: Eddie Knight <knight@linux.com> * Update .github/ISSUE_TEMPLATE/project_incubation.yml Co-authored-by: Eddie Knight <knight@linux.com> * Remove internal operations from archival template Removed internal operations section from project archival issue template. * Clean up project graduation issue template Removed unnecessary markdown sections and checkboxes for internal operations. * Require FINOS Incubating badge adoption in template Updated the project incubation issue template to require the adoption of the FINOS Incubating badge. * Clean up project labs issue template Removed internal operations section and markdown from project labs issue template. * Update software project contribution template Removed internal operations section and checkboxes for FINOS staff. * Update project_graduation.yml --------- Co-authored-by: Juan Estrella <juan.estrella@finos.org> Co-authored-by: Eddie Knight <knight@linux.com>
Member
|
PR #389 has been merged into the This is how we designed the issue contribution process, taking advantage of GitHub issue forms. You can test issue templates on https://github.com/TheJuanAndOnly99/community/issues for now.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR completes the Lifecycle update work by:
This should be the final pass to ultimately close finos/technical-oversight-committee#233 and announce.
Follow on includes: